Techniques for managing software defined networking controller in-band communications in a data center network

ABSTRACT

According to one or more embodiments of this disclosure, a network controller in a data center network establishes a translation table for in-band traffic in a data center network, the translation table resolves ambiguous network addresses based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address. The network controller device receives packets originating from applications and/or an endpoints operating in a network segment associated with a VNID. The network controller device translates, using the translation table, unique loopback addresses and/or routable tenant addresses associated with the packets into routable tenant addresses and/or unique loopback addresses, respectively.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 15/208,018, filed on Jul. 12, 2016, which in turn, claims priority to U.S. Provisional Patent Application Ser. No. 62/342,746, filed on May 27, 2016, the contents of which are herein incorporated by reference

TECHNICAL FIELD

The present disclosure relates generally to communication networks, and more particularly, to data center networks.

BACKGROUND

An ever increasing demand for cloud-based and virtualized services is changing existing network services and storage environments. For example, existing stand-alone storage environments are rapidly being replaced with large storage environments such as data centers, which provide remote access to computing resources through complex and dynamic networks of devices such as servers, routers, switches, hosts, load-balancers, and the like. However, due to dynamic nature and complex network of network devices, data centers present new challenges regarding performance, latency, reliability, scalability, endpoint migration, traffic isolation, and the like.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments herein may be better understood by referring to the following description in conjunction with the accompanying drawings in which like reference numerals indicate identical or functionally similar elements. Understanding that these drawings depict only exemplary embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIG. 1 illustrates an example schematic diagram of a communication network, showing a data center network;

FIG. 2 illustrates a schematic block diagram of an example device, e.g., a network controller device;

FIG. 3 illustrates an example architecture for the communication network shown in FIG. 1;

FIG. 4 an example overlay network architecture, showing various interconnected devices;

FIG. 5 illustrates another example data center network, showing an application centric infrastructure, including a network controller device;

FIG. 6 illustrates an example simplified procedure for managing in-band communications over an overlay network, particularly from the perspective of the network controller device shown in FIG. 5;

FIG. 7 illustrates another example simplified procedure for managing in-band communications over an overlay network, particularly from the perspective of the network controller device shown in FIG. 5;

FIG. 8 illustrates an example network architecture that supports scalable VNID based routing techniques according to another embodiment of this disclosure; and

FIG. 9 illustrates an example simplified procedure for managing in-band communications over an overlay network, particularly from the perspective of the network controller device shown in FIG. 5.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

According to one or more embodiments of this disclosure, a software defined networking controller in a data center network establishes a translation table for in-band traffic in a data center network, the translation table resolves ambiguous network addresses based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address. The network controller device receives packets originating from applications and/or an endpoints operating in a network segment associated with a VNID, and translates, according to the translation table (and using the VNID), unique loopback addresses and/or routable tenant addresses associated with the packets into routable tenant addresses and/or unique loopback addresses, respectively.

According to another embodiment of this disclosure, the software defined networking controller device establishes a virtual routing and forwarding (VRF) device for each network segment of a plurality of network segments and, for each VRF device, instantiates at least one bound interface for routing packets. The network controller device further maps, in a mapping table, a virtual network identifier (VNID) (associated with a first network segment) to a first bound interface of one of the VRF devices, and links at least one application executing on the network controller device with one of the VRF devices. The network controller device also writes a packet from the at least one application to the one of the VRF devices to route the packet over the first bound interface into the first network segment associated with the VNID mapped to the first bound interface.

DESCRIPTION

Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the disclosure.

As used herein the terms “network segment”, “virtual network segment”, and “tenant segment”, including combinations thereof, generally refers to an overlay network within a data center network.

A communication network is a geographically distributed collection of nodes interconnected by communication links and segments for transporting data between end nodes, such as personal computers and workstations, or other devices, such as sensors, etc. Many types of networks are available, with the types ranging from local area networks (LANs) and wide area networks (WANs) to overlay and software-defined networks, such as virtual extensible local area networks (VXLANs).

LANs typically connect the nodes over dedicated private communications links located in the same general physical location, such as a building or campus. WANs, on the other hand, typically connect geographically dispersed nodes over long-distance communications links, such as common carrier telephone lines, optical lightpaths, synchronous optical networks (SONET), or synchronous digital hierarchy (SDH) links. Notably, LANs and WANs can include layer 2 (L2) and/or layer 3 (L3) networks and devices.

The Internet is an example of a WAN that connects disparate networks throughout the world, providing global communication between nodes on various networks. The nodes typically communicate over the network by exchanging discrete frames or packets of data according to predefined protocols, such as the Transmission Control Protocol/Internet Protocol (TCP/IP). In this context, a protocol can refer to a set of rules defining how the nodes interact with each other. Communication networks may be further interconnected by an intermediate network node, such as a router, to extend the effective “size” of each network.

Overlay networks generally allow virtual networks to be created and layered over a physical network infrastructure. Overlay network protocols, such as virtual extensible LAN (VXLAN), network virtualization using generic routing encapsulation (NVGRE), network virtualization overlays (NVO3), stateless transport tunneling (STT), and the like, provide a traffic encapsulation scheme which allows network traffic to be carried across L2 and L3 networks over a logical tunnel. Such logical tunnels can originate and terminate through one or more virtual tunnel endpoints (VTEPs).

Moreover, overlay networks can include virtual segments or network segments, such as VXLAN segments in a VXLAN overlay network, which can include virtual L2 and/or L3 overlay networks over which virtual machines (VMs) communicate. The virtual segments can be identified through a virtual network identifier (VNID), such as a VXLAN network identifier, which can specifically identify an associated virtual network segment or domain.

In this fashion, overlay network protocols provide a traffic encapsulation scheme which allows network traffic to be carried across L2 and L3 networks over a logical tunnel. Such logical tunnels can originate and terminate through virtual tunnel end points (VTEPs). Importantly, in a data center network context, such overlay network protocols provide traffic isolation between network segments associated with different tenants.

FIG. 1 illustrates a schematic diagram of a communication network, particularly a data center network 105. Data center network 105 hosts computing resources (e.g., applications, services, storage, network infrastructure, virtual machines, and the like) and provides one or more remote users (not shown) access to such computing resources. For example, as shown, data center network 105 includes nodes/devices 200 (e.g., routers, sensors, servers, computers, etc.) which operate to route traffic, execute applications, provide storage, and/or otherwise facilitate access to the computing resources in data center network 105.

Operatively nodes/devices 200 communicate over and are interconnected by one or more communication links 106. Communication links 106 may be wired links or shared media (e.g., wireless links, PLC links, etc.) where certain nodes/devices 200 may be in communication with other nodes/devices based on, for example, configuration parameters, distance, signal strength, network/node topology, current operational status, location, network policies, and the like.

Data packets 150, which represent traffic and/or messages, may be exchanged among the nodes/devices 200 in data center network 105 using predefined network communication protocols such as certain known wired protocols (e.g., Interior Gateway Protocol (IGP), Exterior Border Gateway Protocol (E-BGP), TCP/IP, etc.), wireless protocols (e.g., IEEE Std. 802.15.4, WiFi, Bluetooth®, etc.), PLC protocols, VXLAN protocols, or other shared-media protocols where appropriate. In this context, a protocol consists of a set of rules defining how the nodes interact with each other.

Those skilled in the art will understand that any number of nodes, devices, communication links, and the like may be used, and that the view shown herein is for simplicity. Also, those skilled in the art will further understand that while data center network 105 is shown in a particular orientation, such orientation is merely an example for purposes of illustration, not limitation.

FIG. 2 illustrates a schematic block diagram of an example node/device 200 that may be used with one or more embodiments described herein, e.g., as a software defined networking controller device, sometimes referred to as an application policy infrastructure controller (APIC). Device 200 includes one or more network interfaces 210, one or more processors 220, and a memory 240 interconnected by a system bus 250.

Network interface(s) 210 contain the mechanical, electrical, and signaling circuitry for communicating data over links 106 coupled to one or more nodes/devices shown in data center network 105. Network interfaces 210 may be configured to transmit and/or receive data using a variety of different communication protocols, including, inter alia, TCP/IP, UDP, ATM, synchronous optical networks (SONET), VXLAN, wireless protocols, Frame Relay, Ethernet, Fiber Distributed Data Interface (FDDI), etc. Notably, a physical network interface 210 may also be used to implement one or more virtual network interfaces, such as for Virtual Private Network (VPN) access, known to those skilled in the art.

Memory 240 includes a plurality of storage locations that are addressable by processor(s) 220 and network interfaces 210 for storing software programs and data structures associated with the embodiments described herein. Processor 220 may comprise necessary elements or logic adapted to execute the software programs and manipulate the data structures 245. An operating system 242 (e.g., the Internetworking Operating System, or IOS®, of Cisco Systems, Inc.), portions of which are typically resident in memory 240 and executed by the processor(s), functionally organizes the node by, inter alia, invoking network operations in support of software processes and/or services executing on the device. These software processes and/or services may comprise an in-band communication process/service 244, as described herein.

In addition, in-band communication process (services) 244 may include computer executable instructions executed by the processor 220 to perform functions provided by one or more routing protocols, such as various routing protocols as will be understood by those skilled in the art. These functions may, on capable devices, be configured to manage a routing/forwarding table (a data structure 245) containing, e.g., data used to make routing/forwarding decisions

It will be apparent to those skilled in the art that other processor and memory types, including various computer-readable media, may be used to store and execute program instructions pertaining to the techniques described herein. Also, while the description illustrates various processes, it is expressly contemplated that various processes may be embodied as modules configured to operate in accordance with the techniques herein (e.g., according to the functionality of a similar process). Further, while processes may be shown and/or described separately, those skilled in the art will appreciate that processes may be routines or modules within other processes.

Illustratively, the techniques described herein may be performed by hardware, software, and/or firmware, such as in accordance with in-band communication process 244, which may contain computer executable instructions executed by the processor 220 (or independent processor of network interfaces 210) to perform functions described herein.

FIG. 3 particularly illustrates an example architecture 300 for data center network 105. As shown, architecture 300 includes a fabric 305 formed from a physical underlay of networked devices. Here, network fabric 305 includes spine switches 1-N (spine switch-1-spine switch N), and leaf switches 1-N.

Spine switches 1-N can include, for example, layer 3 (L3) switches, and/or they may also perform L2 functionalities (e.g., supporting certain Ethernet speeds, Ethernet Interfaces, etc.). Generally, spine switches 1-N are configured to lookup destination addresses for a received packet in its respective forwarding table and forward the packet accordingly. However, in some embodiments, one or more of spine switches 1-N may be configured to host a proxy function—here, spine switch 1 operates as a proxy switch. In operation, spine switch 1 matches a received packet to a destination address according to its mapping or routing table on behalf of leaf switches that do not have such mapping. In this fashion, leaf switches forward packets with unknown destination addresses to spine switch 1 for resolution.

For example, spine switch 1 can execute proxy functions to parse an encapsulated packet sent by one or more leaf switches, identify a destination address for the encapsulated packet, and route or forward the encapsulated packet according to the same. In some embodiments, spine switch 1 can perform a local mapping lookup in a database (e.g. a routing table, etc.) to determine a correct locator address of the packet and forward the packet to the locator address without changing certain fields in the header of the packet.

Leaf switches 1-N are interconnected with one or more spine switches to form, in part, fabric 305. Leaf switches 1-N can include access ports (or non-fabric ports) and fabric ports. Fabric ports typically provide uplinks to one or more of the spine switches, while access ports provide connectivity for devices such as device 310 (e.g., a host, a virtual machine (VM), a hypervisor, etc.), endpoint(s) 315, as well as one or more “external networks” (labeled as shown). Leaf switches 1-N may reside at an edge of fabric 305, and can thus represent a physical network edge. In some cases, leaf switches 1-N can include top-of-rack (ToR) switches configured according to a ToR architecture. In other cases, leaf switches 1-N can be virtual switches embedded in one or more servers, or even aggregation switches in any particular topology—e.g., end-of-row (EoR) or middle-of-row (MoR) topologies.

As shown, leaf switches 1-N also connect with devices and/or modules, such as endpoint(s) 315, which represent physical or virtual network devices (e.g., servers, routers, virtual machines (VMs), etc.), external networks, and/or other computing resources. Operatively, network connectivity for fabric 305 flows through leaf switches 1-N, where the leaf switches provide access to fabric 305 as well as interconnectivity between endpoints 315, external networks, etc. Notably, leaf switches 1-N are responsible for applying network policies, routing and/or bridging packets in fabric 305. In some cases, a leaf switch can perform additional functions, including, for example, implementing a mapping cache, sending packets to proxy spines (e.g., when there is a miss in the cache), encapsulating packets, enforcing ingress or egress policies, and the like. In addition, one or more leaf switches may perform virtual switching, including tunneling (e.g., VPN tunneling, etc.), which supports network connectivity through fabric 305, as well as supports communications in an overlay network.

An overlay network typically refers to a network of physical or virtual devices (e.g., servers, hypervisors, applications, endpoints, virtual workloads, etc.), which operate in isolated network segments, important for traffic isolation in various network environments (e.g., multi-tenant, etc.). Operatively, overlay networks isolate traffic amongst tenants on respective network segments within physical and/or virtualized data centers. For example, in a VXLAN overlay network, native frames are encapsulated with an outer IP overlay encapsulation, along with a VXLAN header, and UDP header. Generally, each network segment or VXLAN segment is addressed according to a 24-bit segment ID (e.g., a virtual network identifier or VXLAN network identifier (VNID)), which supports up to 16M VXLAN unique and co-existing network segments in a single administrative domain. The VNID identifies the scope of the inner MAC frame originated by an individual VM; thus, overlapping MAC addresses may exist across segments without resulting in traffic cross-over. The VNID is included in an outer header that encapsulates the inner MAC frame originated by a VM. Due to this encapsulation, VXLAN provides a traffic encapsulation scheme that allows network traffic to be carried across L2 and L3 networks over a logical tunnel, where such logical tunnels can originate and terminate through one or more virtual tunnel endpoints (VTEPs), hosted by a physical switch or physical server and/or implemented in software or other hardware.

As mentioned, leaf switches 1-N support network connectivity through fabric 305 and communications in overlay networks, including such isolated network segments. Further, endpoints 315 may be connected to such overlay networks, and can host virtual workloads, clusters, and/or applications/services that communicate in one or more overlay networks through fabric 305.

Notably, although fabric 305 is illustrated and described as an example leaf-spine architecture employing multiple switches, one of ordinary skill in the art will readily recognize that the subject technology employ any number of devices (e.g., server, routers, etc.) and further, the techniques disclosed herein can be implemented in any network fabric. Indeed, other architectures, designs, infrastructures, and variations are contemplated herein. Further, those skilled in the art will appreciate that the devices shown in fabric 305 are for purposes of illustration, not limitation. Any number of other devices (e.g., route reflectors, etc.) can be included (or excluded) in fabric 305, as appreciated by those skilled in the art.

FIG. 4 illustrates an example overlay network architecture 400, including an overlay network 402 interconnecting various network devices/modules—here, host devices 410, 411, and 412. Host devices 410-412 can include, for example, servers, hypervisors, physical switches (e.g., L2/L2 switches), and the like, and can support virtual workloads such as virtual machines, applications, and/or other services executing thereon. Host devices 410-412 may also communicate with other network devices, such as servers 430, 431, 432, and 433, virtual machines (VMs) 440, 441, and the like.

As shown, host devices 410-412 host respective virtual tunnel endpoints (VTEPs) 420, 421, and 422 that communicate in overlay network 402 (which includes one or more leaf switches 1-N of fabric 305 (ref. FIG. 3, above)). VTEPs 420, 421, and 422 represent virtual nodes and/or switches configured to encapsulate and de-encapsulate traffic according to a specific overlay protocol of overlay network 402.

Servers 430-433 and VMs 440, 441 are connected to a respective VTEP and operate in a network segment identified by a corresponding VNID. Notably, each VTEP can include one or more VNIDs—e.g., VTEPs 420 and 422 include VNID 1 and VNID 2, while VTEP 421 includes VNID 1. As discussed above, traffic in overlay network 402 is logically isolated according to network segments identified by specific VNIDs. For example, network devices residing in a network segment identified by VNID 1 cannot be accessed by network devices residing in a network segment identified by VNID 2. More specifically, as shown, server 430 can communicate with server 432 and VM 440 because these devices each reside in the same network segment identified by VNID 1. Similarly, server 431 can communicate with VM 441 because these devices reside in the same network segment identified by VNID 2.

VTEPs 420-422 operatively encapsulate/decapsulate packets for respective network segments identified by respective VNID(s) and exchange such packets in the overlay network 402. As an example, server 430 sends a packet to VTEP 420, which packet is intended for VM 440, hosted by VTEP 422. VTEP 420 determines the intended destination for the packet (VM 440), and encapsulates the packet according to its routing table (e.g., which includes an endpoint-to-switch mappings or bindings for VTEP 422, hosting VM 440), and forwards the encapsulated packet over overlay network 402 to VTEP 422. VTEP 422 encapsulates the packet, and routes the packet to its intended destination—here, VM 440.

In some embodiments, however, the routing table may not include information associated with an intended destination. Accordingly, in such instances, VTEP 410 may be configured to broadcast and/or multicast the packet over overlay network 402 to ensure delivery to VTEP 422 (and thus, to VM 440). In addition, in preferred embodiments, the routing table is continuously and dynamically modified (e.g., removing stale entries, adding new entries, etc.), in order to maintain up-to-date entries in the routing table.

Notably, as is appreciated by those skilled in the art, the views shown herein are provided for purposes of illustration and discussion, not limitation. It is further appreciated that the host devices, servers, and VMs shown in FIG. 4 may represent a single server or VM, and/or multiple servers or VMs, such as a cluster of servers/VMs. Moreover, the VMs may be operatively configured to support virtual workloads, application workloads, resources, and/or services. In addition, in some cases, servers 430-433 can similarly host virtual workloads through respective VMs executing thereon.

As discussed above, data centers include a dynamic and complex network of interconnected devices, which present new challenges regarding performance, latency, reliability, scalability, endpoint migration, traffic isolation, and the like. Increasingly, data centers employ overlay networks to provide proper traffic isolation in multi-tenant environments. Typically, as mentioned, in such multi-tenant environments, traffic (e.g., data packets, etc.) is encapsulated and isolated for a particular network segment using an overlay protocol. Operatively, such overlay protocol often encapsulates a packet with network identifier (e.g., a virtual network identifier (VNID), etc.) to communicate the packet in a specific network segment. Challenges arise in data center networks and overlay networks, due to the complexity of interconnected devices as well as the dynamic nature of resource migration, on-demand scalability, and the like. Accordingly, the techniques described herein particularly provide improvements for managing in-band communications in data center networks (including overlay networks).

Specifically, the techniques described herein dynamically track end-point migration, preserve traffic isolation, and route and/or forward communications amongst network devices/modules (e.g., applications, network controller devices, virtual machines (VMs), and the like). In particular, these techniques are preferably employed by one or more network controller devices, which connect to a network fabric in a data center network. These techniques further offload tasks such as locating endpoints for respective leafs (and/or network controller devices) to one or more proxy devices (or devices with proxy functionality). For example, according to some embodiments discussed in greater detail below, a network controller performs address translation to identify routable addresses, encapsulates packets according to VXLAN encapsulation protocols, and forwards the encapsulated packets to a well-known proxy device (e.g., a proxy spine switch) for address resolution. The proxy device receives the encapsulated packets, determines the appropriate routable addresses, and forwards the encapsulated packets to an endpoint in an appropriate network segment based on a VNID. In operation, the proxy devices maintain, or otherwise update respective routing tables with real-time locations (e.g., addresses) for endpoints in the data center network.

FIG. 5 illustrates another example data center network 500, showing an application centric infrastructure that employs an application policy based solution with scalable distributed enforcement. Generally, data center network 500 supports integration of physical and virtual environments under one declarative policy model for networks, servers, services and security.

Data center network 500 comprises a network fabric 505 that employs an overlay protocol such as a VXLAN overlay protocol. As discussed above, a VXLAN overlay protocol encapsulates/decapsulates and routes packets according to a VXLAN network identifier (VNID) carried in a header field. The VNID identifies a specific virtual network or network segment associated with one or more tenants. In addition, data center network 500 also includes one or more software defined networking controller devices, also referred to as application policy infrastructure controllers (APICs)—here, APIC 1-3—which provide a single point for automation and management.

Fabric 505 includes spine switches 1-N and leaf switches 1-N. As shown, spine switch 1 is designated as a proxy devices or a VXLAN proxy switch (in the VXLAN overlay protocol). Operationally, unknown VXLAN traffic in fabric 505 is forwarded to proxy switches for address resolution and further routing in the data center network and/or within respective overlay networks.

Leaf switches 1 and 2 are further connected to one or more network controller devices APICs 1, 2, and 3, and leaf switches 3 and 4 are connected to host devices 1 and 2. Host devices 1 and 2 can include, for example, physical or virtual devices such as servers, switches, routers, virtual machines, and the like. Here, hosts 1 and 2 host or execute two service VMs 511 and 512. Each VM 511 and VM 512 serves different tenants associated with respective tenant segments in an overlay network.

Overlay networks, as discussed above, are often employed in data center networks to isolate traffic amongst tenants. Typically, a network segment or tenant segment is associated with a tenant using a VNID. In data center network 500, VM 511 communicates in a network segment in common with application (“app”) 501, which executes on one or more of APICs 1, 2, and/or 3, and VM 512 communicates in a network segment in common with application (“app”) 502, which also executes on one or more APICs 1, 2, and/or 3. Due to network segment isolation, VM 511 and VM 512 may be assigned the same IP address—here, 1.1.1.10.

In operation, app 501 and app 502 send in-band communications (e.g., data packets) over network fabric 505 to respective service VMs 511, 512, and likewise, VMs 511, 512 send in-band communications over network fabric 505 to app 501, 502, respectively. Typically, communications between respective applications and VMs are maintained (e.g., persistent) even if the VM migrates amongst hosts in order to maintain proper routing information.

Regarding traffic isolation for in-band communications, the techniques herein (such as the in-band communication process/services 244) employ a VNID based address translation, where overlapping or shared tenant addresses—here, 1.1.1.10 for VMs 511, 512—are translated into a unique (e.g., different) loopback address according to translation tables indexed or keyed to one or more VNIDs.

For example, a network controller device such as APIC 1 establishes a translation table for in-band traffic in data center network 500 to translate potentially ambiguous addresses. Here, APIC 1 establishes a translation table 520 that includes entries indexed according to a unique address (e.g., loopback address), a VNID for a tenant segment, and/or a routable tenant address. Notably, the routable tenant address in routing table 520 is a public address while the unique address is a private address within data center network 500.

As discussed, although the same or common routable addresses (1.1.1.10, and 1.1.1.1) may be used to identify more than one app, VM, or other computing resource in data center network 500, an encapsulation scheme (e.g., VXLAN) for a packet carrying the common routable address will also include a VNID in a header field. The network controller devices use the common routable address along with the VNID to translate the common routable address into a corresponding unique address. Alternatively (or in addition), the network controller devices may similarly translate a unique address into a common routable address and a VNID so that network devices within fabric 505 can properly route/forward the packet to an appropriate endpoint.

For example, a packet from VM 511 (1.1.1.10) is encapsulated with VNID 10001, while a packet from VM 512 (1.1.1.10) is encapsulated with VNID 10002. The proxy spine switch 1 receives the packets from VM 511 and/or VM 512 and forwards to one of the APICs shown for further translation (APIC 1 for example). APIC 1 receives and decapsulates the packets from proxy spine switch 1 to determine respective VNIDs and routable tenant addresses. APIC 1 further translates the routable tenant addresses based on the VNID into unique addresses (e.g., loopback addresses) for respective applications, and forwards the message to the appropriate application(s). Here, for example, an encapsulated packet originating from VM 511 will have a VXLAN header indicating VNID 10001, an inner source address field of 1.1.1.10, and an inner destination address field of 1.1.1.1, while an encapsulated packet originating from VM 512 will have a VXLAN header indicating 10002, an inner source field of 1.1.1.10 and an inner destination address field of 1.1.1.1. The APIC receiving such packets will translate the inner source/destination address fields (e.g., which include routable addresses) into unique loopback addresses based on translation table 520. Specifically, the inner source address field of 1.1.1.10 in VNID 10001 translates into 192.168.1.2 (corresponding to VM 511), and the inner destination address field of 1.1.1.1 in VNID 10001 translates into 192.168.1.1 (corresponding to app 501). In this fashion, the network device controllers (APICs) can translate potentially ambiguous routable tenant addresses (e.g., common or shared by more than one network device) into a unique address/loopback address.

Similarly, applications—here, apps 1, 2—can likewise have a shared or common routable tenant address when operating in different network segments. For example, the same address for app 501, 502 (1.1.1.1) is translated into different loopback addresses (192.168.1.1 and 192.168.1.3) for different tenant segments based on the VNID associated with a particular network segment. Here, app 501 and app 502 are bound to IP address 192.168.1.1 and 192.168.1.3, respectively, and communicate with VM 511, 512, respectively. App 501 sends a packet intended for VM 511 to one of the network controller devices (e.g., APIC 1) for address translation. The packet from app 501 includes 192.168.1.1 and 192.168.1.2 as an inner source and a destination IP address, respectively. APIC 1 receives the packet from app 501 and translates the inner source and destination IP address into routable tenant addresses 1.1.1.1 and 1.1.1.10, respectively. APIC 1 further encapsulates the packet from app 501 with VNID 10001 in a VXLAN header based on translation table 520.

The in-band communication techniques discussed above consolidate address translation in one or more network controller devices while respecting traffic isolation between different network segments. Notably, the translation tables used by the network controller devices may be local and/or distributed across multiple networks devices. Further, as discussed, the routing tables include entries keyed or indexed according to VNIDs, routable tenant addresses, and/or unique (loopback) addresses. Based on a combination of a VNID, a routable tenant address, and/or a unique address, the network controller device can translate between routable tenant addresses and unique addresses and/or identify an appropriate VNID for a packet (which VNID is used when encapsulating the packet for forwarding to the proxy device(s)).

FIG. 6 illustrates an example simplified procedure 600 for managing in-band communications over an overlay network, particularly from the perspective of a network controller device (e.g., APIC(s) 1-3). Procedure 600 begins at step 605 and continues on to step 610 where, as discussed above, the network controller device establishes a translation table (e.g., local, distributed, etc.) for resolving network addresses for in-band traffic in a data center network based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address.

Procedure 600 continues to step 615, where operatively, the network controller device receives a packet originating from an application associated with a first unique loopback address. Notably, the packet is also intended for an endpoint in a first network segment associated with a first VNID, and the endpoint is associated with a second unique loopback address. The network controller, in steps 620 and 625, further translates, using the translation table (e.g., translation table 520), the first unique loopback address into a first routable tenant address and a first VNID, and the second unique loopback address into a second routable tenant address and the first VNID based the first unique loopback address and the second unique loopback address, respectively. Once translated, the network controller encapsulates (e.g., VXLAN encapsulation), in step 625, the packet as an encapsulated packet having a header field including the first VNID, an outer address field including an address for a proxy device (to forward to a proxy device in the network fabric), an inner source address field including the first routable tenant address, and an inner destination field including the second routable tenant address.

The network controller device further forwards the encapsulated packet, in step 635, to the proxy device to route the encapsulated packet in the data center network to the endpoint in the first network segment associated with the first VNID. The proxy device, as discussed above, receives and decapsulates the packet to determine appropriate routing/forwarding and sends the packet to the endpoint. Notably, in some embodiments, the proxy device tunnels the packet to the endpoint (e.g., in the overlay network/first network segment).

In addition, the proxy device may also update its routing table, in step 640, based on migration of the endpoint from the first network segment to a second network segment, or other such dynamic movement of computing resources. Procedure 600 subsequently ends at step 645, but may continue on to step 615 where the network controller device receives packets from the application (or other applications).

FIG. 7 illustrates another example simplified procedure 700 for managing in-band communications over an overlay network, again from the perspective of a network controller device (e.g., APIC(s) 1-3). Here, procedure 700 describes steps for translating in-band traffic from one or more endpoints (e.g., VMs 511, 512, etc.) to one or more applications (e.g., app 1, app 2, etc.).

Procedure 700 begins at step 705 and continues on to step 710 where, similar to procedure 600, the network controller device establishes a translation table (e.g., local, distributed, etc.) for resolving network addresses for in-band traffic in a data center network based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address. Notably, the translation table may be the same as the one provided in procedure 600.

Procedure 700 continues to step 715 where the network controller device decapsulates a second packet originating from the endpoint in first network segment to determine the first VNID, the second routable tenant address, and the first routable tenant address.

The network controller device further translates, in steps 720, 725 the first routable tenant address and the second routable tenant address (e.g., using translation table 520) into the first unique loopback address and the second unique loopback address, respectively, based at least on the first VNID. The network controller device further forwards the second packet to the appropriate application associated with the first unique loopback address. Procedure 700 subsequently ends at step 735, but may continue on to step 715 where the network controller device decapsulates packets from endpoints in corresponding network segments.

It should be noted that certain steps within procedures 600-700 may be optional, and further, the steps shown in FIGS. 6-7 are merely examples for illustration—certain other steps may be included or excluded as desired. Further, while a particular order of the steps is shown, this ordering is merely illustrative, and any suitable arrangement of the steps may be utilized without departing from the scope of the embodiments herein. Moreover, while procedures 600-700 are described separately, certain steps from each procedure may be incorporated into each other procedure, and the procedures are not meant to be mutually exclusive.

In addition to the embodiments described above, additional embodiments of this disclosure provide a scalable VNID mapping table proportional in size with VNIDs for network segments and/or VRF instances in an overlay network. For example, according to one of these embodiments, the in-bound communication techniques leverage Linux VRF instances and a universal TUN/TAP driver and, in particular, tie the fabric VRF instances and the Linux VRF instances together by mapping a TAP interface with a VNID for a network segment.

In detail, FIG. 8 illustrates an example network architecture 800 that supports scalable VNID based mapping techniques. As shown in network architecture 800, apps 501, 502, 810, and 811 communicate over respective interfaces (e.g., TAP/TUN interfaces, bond interface 805, etc.) with one or more computing resources—here, service virtual machines (VMs) 511-N. Network architecture also includes an in-band module 815 (e.g., a user space daemon, etc.) that manages and/or otherwise coordinates forwarding traffic between the applications, including respective VRF devices 801, 802, 812, and VMs 511, 512 (through VM-N).

In operation, a network controller (not shown) (e.g., one of APICs 1-3) creates a Linux VRF instance for each fabric VRF instance. As discussed below, a fabric VRF instance refers to a context for a network segment associated with a VNID (e.g., a tenant network segment). As shown, Linux VRF instances incorporate the fabric VRF context in a VRF device—e.g., VRF devices 801, 802, and 812. The network controller further creates or instantiates an enslaved interface for each VRF instance/device—e.g., interface 1, interface 2, interface 3—which are illustrated as TAP/TUN interfaces. Applications (apps 501, 502, 810, 812) are tied, respectively, to interfaces on corresponding VRF devices. Notably, apps 810 and 811 operate in the same network segment (e.g., VNID 10003) and shown as tied or bound to a shared interface 3 on VRF device 812.

In general, in-band module 815 executes or runs on the network controller and constructs a mapping table 820 to map interfaces with VNIDs (associated with respective network segments). In-band module 815 maintains mapping table 820 and performs VXLAN tunneling for traffic exchanged between applications and computing resources (here, VMs). In-band module 815 updates entries in mapping table 820 when interfaces are created (and/or deleted).

As shown, mapping table 820 maps an aggregation of interfaces to respective VNIDs used by the fabric VRF. Mapping table 820 maps each interface with a corresponding VNID associated with a network segment. For example, interface 1 is mapped to VNID 10001 used by the fabric VRF or network segment common with VM 511. Accordingly, in-band module 815 directs traffic destined for app 501 (which operates in the network segment associated with VNID 10001) to interface 1. In greater detail, consider a packet (e.g., a VXLAN encapsulated packet) sent from VM 511 to app 501, coming in from a channel bonding interface 805 (e.g., which represents a channel bonding interface and/or an aggregation of interfaces). In-band module 815 listens, monitors, or otherwise receives the encapsulated packet from bond interface 805 on an UDP socket bound to a reserved port number. In-band module 815 further performs decapsulation (e.g., VXLAN decapsulation) and determines the VNID—here, VNID 10001—from the encapsulated packet header. In-band module 815 identifies an associated interface (e.g., interface 1) and corresponding enslaved VRF device (e.g., VRF device 1) based on a mapping table lookup. In-band module 815 then writes the decapsulated packet into interface 1, which is received by app 501 tied to VRF device 801. Conversely, app 501 sends a packet to VM 511, the packet is forwarded to interface 1 because interface 1 is the next hop of a default route in VRF device 801. The packet is picked up by in-band module 815, which listens to traffic on interface 1. In-band module 815 performs VXLAN encapsulation, using VNID 10001 in the VXLAN header. The VNID for the received packet is determined by mapping table 820 and a lookup, using interface 1 as the key. In-band module 815 further sends the encapsulated packet through the UDP socket to bond interface 805.

As shown in mapping table 820, each VNID is mapped to a single interface. In this fashion, mapping table 820 remains proportional to a number of VRF instances (e.g., network segments) mapped to respective interfaces. Given a large number of fabric VRF instances, mapping table 820 scales efficiently, because its size is unrelated to the number of service VMs in a fabric VRF.

FIG. 9 is an example of simplified procedure 900 for managing in-band communications over an overlay network, particularly from the perspective of a network controller device (e.g., one of APICs 1-3 shown in FIG. 5).

Procedure 900 begins at step 905 and continues on to step 910 where, as discussed above, the network controller device establishes a virtual routing and forwarding (VRF) instance for each network segment of a plurality of network segments. The network controller, at step 915, further instantiates, for each VRF instance, at least one bound interface on a VRF device. As discussed, the bound interface can include, for example, a TAP/TUN interface (e.g., interfaces 1-3 in FIG. 8), which are enslaved to respective VRF devices. Procedure 900 continues to step 920 where the network controller device maps one or more virtual network identifiers (VNIDs) to one or more respective bound interfaces on corresponding VRF devices. For example, referring again to mapping table 820, the network controller device (e.g., and/or in-band module 815, which executes on the network controller device) maps an interface on respective VRF device to a VNID associated with a network segment.

Further, in step 925, the network controller device links or associates one or more applications with the VRF device, and thus, links the one or more applications the respective interface(s) on the VRF device. Procedure 900 continues to step 930 where the network controller and/or the application executing/running on the network controller sends or writes a packet to the linked VRF device, which is a default next hop, in order to route the packet in a network segment over an interface of the VRF device. Typically, an in-band module executing on the network controller device listens to the tap interface, receives the packet, determines the VNID mapped to the interface from a mapping table (e.g., mapping table 820), and tunnels the packet to an appropriate computing resource (e.g., a service VM). Procedure 900 subsequently ends at step 935, but may continue on to step 910 where the network controller device establishes VRF instances for network segments, discussed above.

It should be noted that certain steps within procedure 900 may be optional, and further, the steps shown in FIG. 9 are merely examples for illustration—certain other steps may be included or excluded as desired. Further, while a particular order of the steps is shown, this ordering is merely illustrative, and any suitable arrangement of the steps may be utilized without departing from the scope of the embodiments herein. In addition, although procedure 900 is described with respect to a network controller device, certain operations may be executed by devices or modules running on the network controller device (e.g., in-band module 815, etc.).

The techniques described herein manage in-band traffic in a data center network, and in particular, traffic within network segments. These techniques further support endpoint migration for in-band communications using local and/or aggregated translation and mapping tables that may index entries according to VNIDs, tenant addresses, unique (loopback) addresses, bound network interfaces (TAP/TUN interfaces), and combinations thereof.

While there have been shown and described illustrative embodiments for managing in-band communications in a data center network, it is to be understood that various other adaptations and modifications may be made within the spirit and scope of the embodiments herein. For example, the embodiments have been shown and described herein with relation to network switches and a control plane comprising the network switches. However, the embodiments in their broader sense are not as limited, and may, in fact, be used with any number of network devices (e.g., routers), and the like. In addition, the embodiments are shown with certain devices/modules performing certain operations (e.g., APICs 1-3, proxy spine switch 1, in-band module 715, and the like), however, it is appreciated that various other devices may be readily modified to perform operations without departing from the sprit and scope of this disclosure. Moreover, although the examples and embodiments described herein particularly refer to VXLAN protocols, the embodiments in their broader sense may be applied to any known encapsulation protocols, as is appreciated by those skilled in the art.

The foregoing description has been directed to specific embodiments. It will be apparent, however, that other variations and modifications may be made to the described embodiments, with the attainment of some or all of their advantages. For instance, it is expressly contemplated that the components and/or elements described herein can be implemented as software being stored on a tangible (non-transitory) computer-readable medium, devices, and memories (e.g., disks/CDs/RAM/EEPROM/etc.) having program instructions executing on a computer, hardware, firmware, or a combination thereof. Further, methods describing the various functions and techniques described herein can be implemented using computer-executable instructions that are stored or otherwise available from computer readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on. In addition, devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example. Instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures. Accordingly this description is to be taken only by way of example and not to otherwise limit the scope of the embodiments herein. Therefore, it is the object of the appended claims to cover all such variations and modifications as come within the true spirit and scope of the embodiments herein. 

The invention claimed is:
 1. A method comprising: receiving, by a network controller device, a packet intended for an endpoint; translating, by the network controller device using a table, a first loopback address into a first routable tenant address; translating, by the network controller device using the table, a second loopback address into a second routable tenant address; encapsulating the packet as an encapsulated packet having a header field, an outer address field including an address for a proxy device, an inner source address field including the first routable tenant address, and an inner destination field including the second routable tenant address; forwarding, by the network controller device, the encapsulated packet to the proxy device; and updating a routing table of the proxy device based on migration of the endpoint.
 2. The method of claim 1, further comprising: decapsulating, by the network controller device, a second packet originating from the endpoint to determine the second routable tenant address and the first routable tenant address; translating, by the network controller device using the table, the first routable tenant address into the first loopback address based on at least the first routable tenant address; translating, by the network controller device using the table, the second routable tenant address into the second loopback address based on at least the second routable tenant address; and forwarding, by the network controller device, the second packet to an application associated with a first unique loopback address.
 3. The method of claim 1, wherein updating of the routing table of the proxy device based on the migration of the endpoint is performed via the proxy device.
 4. The method of claim 1, wherein forwarding the encapsulated packet to the proxy device further causes the proxy device to decapsulate the encapsulated packet to determine a virtual network identifier (VNID) and the second routable tenant address.
 5. The method of claim 1, further comprising: establishing, by the network controller device, the table for resolving network addresses for in-band traffic in a data center network based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address; and indexing, in the table, each loopback address of a plurality of loopback addresses according to one respective VNID and one respective tenant address.
 6. The method of claim 5, wherein the VNID is a virtual extensible LAN (VXLAN) identifier.
 7. The method of claim 1, wherein the endpoint is a virtual machine (VM) hosted by a leaf node in a data center network.
 8. A network controller device comprising: one or more computer processors; and a memory storing instructions that, when executed by the one or more computer processors, cause the network controller device to: receive a packet intended for an endpoint, translate, using a table, a first loopback address into a first routable tenant address, translate, using the table, a second loopback address into a second routable tenant address, encapsulate the packet as an encapsulated packet having a header field including an outer address field including an address for a proxy device, an inner source address field including the first routable tenant address, and an inner destination field including the second routable tenant address, forward the encapsulated packet to the proxy device, and update a routing table of the proxy device based on migration of the endpoint.
 9. The network controller device of claim 8, wherein the instructions further cause the network controller device to: decapsulate a second packet originating from the endpoint in to determine the second routable tenant address and the first routable tenant address; translate, using the table, the first routable tenant address into the first loopback address based on at least the first routable tenant address; translate, using the table, the second routable tenant address into the second loopback address based on at least the second routable tenant address; and forward the second packet to an application associated with a first unique loopback address.
 10. The network controller device of claim 8, wherein the proxy device updates the routing table of the proxy device based on the migration of the endpoint from a first host to a second host.
 11. The network controller device of claim 8, wherein forwarding the encapsulated packet to the proxy device further causes the proxy device to decapsulate the encapsulated packet to determine a virtual network identifier (VNID) and the second routable tenant address.
 12. The network controller device of claim 8, wherein the instructions further cause the network controller device to: establish the table for resolving network addresses for in-band traffic in a data center network based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address; and index, in the table, each loopback address of a plurality of loopback addresses according to one respective VNID and one respective tenant address.
 13. The network controller device of claim 12, wherein the VNID is a virtual extensible LAN (VXLAN) identifier.
 14. The network controller device of claim 8, wherein the endpoint is a virtual machine (VM) hosted by a leaf node in a data center network.
 15. A non-transitory computer-readable medium storing instructions that, when executed by a network controller device, cause the network controller device to: receive a packet intended for an endpoint; translate, using a table, a first loopback address into a first routable tenant address; translate, using the table, a second loopback address into a second routable tenant address; encapsulate the packet as an encapsulated packet having a header field including an outer address field including an address for a proxy device, an inner source address field including the first routable tenant address, and an inner destination field including the second routable tenant address; forward the encapsulated packet to the proxy device; and update a routing table of the proxy device based on migration of the endpoint.
 16. The non-transitory computer-readable medium of claim 15, wherein the instructions further cause the network controller device to: decapsulate a second packet originating from the endpoint to determine the second routable tenant address and the first routable tenant address; translate, using the table, the first routable tenant address into the first loopback address based on at least the first routable tenant address; translate, using the table, the second routable tenant address into the second loopback address based on at least the second routable tenant address; and forward the second packet to an application associated with a first unique loopback address.
 17. The non-transitory computer-readable medium of claim 15, wherein the proxy device updates the routing table of the proxy device based on the migration of the endpoint from a first host to a second host.
 18. The non-transitory computer-readable medium of claim 15, wherein forwarding the encapsulated packet to the proxy device further causes the proxy device to decapsulate the encapsulated packet to determine a virtual network identifier (VNID) and the second routable tenant address.
 19. The non-transitory computer-readable medium of claim 15, wherein the instructions further cause the network controller device to: establish the table for resolving network addresses for in-band traffic in a data center network based on one or more of a virtual network identifier (VNID), a routable tenant address, or a unique loopback address; and index, in the table, each loopback address of a plurality of loopback addresses according to one respective VNID and one respective tenant address.
 20. The non-transitory computer-readable medium of claim 19, wherein the VNID is a virtual extensible LAN (VXLAN) identifier. 